MB File Manager

Select MB File Manager (the fourth option) in the Rescue USB startup menu.
It is also available from the tool picker inside Windows PE. Close it to
return to that picker. On normal Windows it can be run from
engine\MB.FileManager.exe in the MBUT folder.

Open a source folder in one pane and a destination folder in the other.
Select files or folders, click Copy (or Ctrl+C), then click the destination
pane and Paste (or Ctrl+V). Right-click Copy and Paste are also supported.
Drive letters in rescue Windows can differ from installed Windows.
Use the address box to enter a folder path and press Enter.

Folder copies include subfolders and empty folders. Existing folders merge;
existing files prompt for replacement or skipping. The answer applies to
remaining file conflicts in that copy. Cancel stops at the next file read.
Completed files remain; an unfinished file is removed. Existing files are
replaced only after their new contents have been written successfully.

Copy details lists skipped files and errors (up to 500 details). Inaccessible,
locked, encrypted or damaged files may be unavailable. Links and junctions
are deliberately not followed. MB File Manager does not unlock BitLocker,
bypass permissions, or recover deleted files; use Data Recovery for recovery.
This copies file contents and modification times, not a full Windows system
backup with permissions, alternate streams and filesystem metadata.

MBUT disk-check reports are saved automatically in logs beside MBUT.exe.
Each run has its own dated subfolder. Keep the toolkit on another device
when diagnosing a drive containing files you need to recover. Existing
source-drive protection remains in place.

The ISO includes the four-entry menu files for UEFI USB creation with Rufus.
Direct optical/virtual-CD ISO boot opens the Windows PE tool picker instead;
memory testing remains a separate USB startup option.

Known outstanding issue: the older Windows boot components have not been
updated in this release. Rufus's revoked-bootloader warning remains under
investigation. The virtual-machine boot test does not establish compatibility
with the latest Secure Boot revocations on every PC.
